As HAProxy is running chrooted by default, we rely on an additional syslog
socket created by rsyslog inside the chroot for logging. As this socket cannot
trigger syslog activation, we explicitly order HAProxy after rsyslog.service.
Note that we are not using syslog.service here, since the additional socket is
rsyslog-specific.
Forwarded: no
Last-Update: 2017-12-01
Gbp-Pq: Name haproxy.service-start-after-syslog.patch
* BUG/MAJOR: mux-h2: properly handle short reads on PING frames
* BUG/MAJOR: h1-htx: report an error on a too long chunk-size line
* BUG/MAJOR: h3: check body size with content-length on empty FIN
(CVE-2026-33555)